Sourced from org.apache.logging.log4j:log4j-bom's releases.

2.24.1

This release contains mainly bug fixes of problems encountered with the thread context map, logger registry and configuration reloading.

It also enhances integration tests to use Docker images of the most recent releases of MongoDB and Elastic Search.

Changed

• Rework LoggerRegistry to make it MessageFactory-namespaced. This effectively allows loggers of same name, but different message factory. (#2936)
• Enable Docker-based tests in CI for JSON Template Layout (#2953)

Fixed

• Switch MongoDB tests to use Docker. (#2229)
• Fix reloading of the configuration from an HTTP(S) source (#2937)
• Fix putAll() in the default thread context map implementation (#2942)

Updated

• Update org.apache.logging:logging-parent to version 11.3.0

2.24.0

The 2.24.0 version of Log4j API has been enhanced with changes from the 3.x branch and will be used by both Log4j 2 Core and Log4j 3 Core releases. The changes include:

• A faster default ThreadContextMap.
• Enhanced GraalVM support: native binaries that use Log4j API will no longer require additional GraalVM configuration.
• The configuration properties subsystem now only accepts the official pre-2.10 property names and the normalized post-2.10 names. Check your configuration for typos.

Documentation

The Apache Log4j 2 website has been almost entirely rewritten to provide improved documentation and faster access to the information you need.

Bridges

The JUL-to-Log4j API and Log4j 1-to-Log4j API bridges will no longer be able to modify the configuration of Log4j Core by default. If such a functionality is required, it must be explicitly enabled.

Modules

The following Log4j Core additional modules have been removed:

• log4j-flume-ng The module is no longer part of the release process and will follow its own release lifecycle. Please manage your dependencies using log4j-bom to always use its latest version.

• log4j-kubernetes The module has been moved to the Fabric8.io Kubernetes project and follows the Fabric8.io release lifecycle.

• log4j-mongodb3

... (truncated)

• 8ee9387 Update the project.build.outputTimestamp property
• 767be86 Prepare release notes version 2.24.1
• a92713c Pin Cassandra transitive deps
• a05d921 Revert "Prepare release notes for 2.24.1"
• 755497d Revert "Single constructor for ConfigurationSource"
• a01f7e4 Prepare release notes for 2.24.1
• 5d6bd3c Clean up changelog entries
• 9c798ae Update com.github.luben:zstd-jni to version 1.5.6-6 (#2998)
• a3d138b Update commons-io:commons-io to version 2.17.0 (#2984)
• 13b5fda Update org.slf4j:slf4j-nop to version 2.0.16 (#2955)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)